โ RNS 1.4.2 released https://pypi.org/project/rns/
๐ฌค rns.recipes
top
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ Faketec Porting โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Started by anonymoose ยท 25d ago
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-1
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ anonymoose #1 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 25d ago
Hello. I built some faketec devices. I want to add support for the board to
RNode_Firmware. It seems like to add support for a new device there are many files to
edit, and it's not clear if everything is done until building, and then getting errors.
Has anyone successfully ported RNode to a faketec or other new board? Can you give me
pointers on what I'm missing?
-
Details
I added the board to Boards.h, and added an entry to the Makefile. It builds but I get
issues with the defines for PRODUCT, MODEL, and BOARD. It seems these are just tags to
tell other parts of the code what to do. But it's not clear where in the code needs to be
changed to add support for other boards.
If I try to create my own PRODUCT, MODEL, and BOARD, I get invalid eeprom errors.
The provisioning process is dark magic to me. I cannot find documentation on the inner
workings of RNode and don't really know what I need to start doing.
-
Maybe for something better discussed in a seperate thread: Is there a reason why the
details for all the boards are in one header file? Would it be possible to seperate the
Boards.h file into a seperate header file for each board, so it's easier to add support
for new boards?
โ 0 โ 0 โค 0
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-2
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ anonygoose #2 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 25d ago
You're on the right track. You should pick another board id and just search all the code
for it. This is pretty easy when the project is open in Arduino IDE or most other
editors. If you use something like Arduino IDE, you can build directly in the editor and
not mess with the Makefile right away. You will need to add PRODUCT, MODEL and BOARD
values that are distinct from the other RNode devices if you want to eventually return
the code to one of the upstream repos. Those IDs are also used in rnodeconf.py for
provisioning. If they firmware is fully updated and rnodeconf is modified to provision
it, the eeprom errors will go away. The second path would be to modify a copy of the web
flasher to do the same thing. It also has hardcoded IDs, so must be modified to flash.
I personally think the one header file is easier to work with, since you can compare all
the models and take pieces that match your board and copy them in to your own block.
There could be multiple files, but that would be quite a lot of smaller files with how
many board models are supported now.
โ 1 โ 0 โค 0
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-3
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ Nickie #3 โ
โ c28ea15c1b83aaba โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 22d ago
Faketec has been working in my [fork](https://git.rns.moscow/deuxyeux/RNode_Firmware) for
a while now. You can flash it [here](https://flasher.rns.moscow/)
โ 1 โ 0 โค 0
โ INFO โ Identify to this node to post. How?
bottom